Collaborative phone-based file exchange

ABSTRACT

A collaborative phone-based file exchange technique that wirelessly synchronizes a user&#39;s work context with his or her mobile phone and makes this context readily available and sharable in collaborative situations. When the user is away from their desk, collaboration with others is possible by sharing/downloading between the mobile phone and a paired PC, which may be a colleague&#39;s computer or a meeting room workstation/computer. When the user returns to their office, any recently downloaded files are automatically synchronized back to their office PC.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a Continuation application of U.S. patent application Ser. No. 14/290,075, filed on May 29, 2014, by Amy Kathleen Karlson, and entitled “COLLABORATIVE PHONE-BASED FILE EXCHANGE”, and claims priority to U.S. patent application Ser. No. 14/290,075 under Title 35 U.S.C. § 120. Further, U.S. patent application Ser. No. 14/290,075 is a Divisional of U.S. Pat. No. 8,782,527, filed Jun. 27, 2007, and claims priority to U.S. Pat. No. 8,782,527 under Title 35 U.S.C. § 120.

BACKGROUND

Mobile phone ownership was a relative rarity 10 years ago. At that time there was about one mobile phone for every five people in the United States. Since then, mobile phone proliferation has continued relentlessly, with many markets nearing saturation worldwide. Parallel advances in cell phone technology have seen such explosive improvements in processing speed, storage capacity, connectivity, battery life and screen resolution that many modern cell phones are more computationally advanced than the desktop computers of 10 years ago. Despite the fact that mobile phones have become a ubiquitous accessory, however, they remain largely underutilized as productivity and collaboration agents.

Every business depends on the free flow of information and ideas to improve their products and services. Effective collaboration between people increases product quality, improves product or project development lead times, and reduces costs. However, effective collaboration is often difficult. For example, a user's work context, including the various documents, emails, links and context history involved in accomplishing work tasks, is typically confined to their office PC, which makes this information difficult to share with others. Furthermore, networking technology is not yet at the point where ubiquitous connectivity to support collaboration can be guaranteed. For example, corporate environments are firewalled, neither WiFi nor cellular data network coverage is universal, and users must opt into cellular data plans at additional cost.

SUMMARY

This Summary is provided to introduce a selection of concepts in a simplified form that are further described in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

The present collaborative phone-based file exchange technique uses a mobile phone to provide reliable access to a user's personal data and annex nearby resources to support a rich collaboration experience. The present collaborative phone-based file exchange technique wirelessly synchronizes a user's recent work context on their personal computer (PC), or similar computing device, with his or her mobile phone, and makes this context readily available and sharable in collaborative situations. When the user is away from their PC, collaboration with others is possible by sharing/downloading files between the mobile phone and a PC enabled with a collaborative phone-based file exchange application using a short range wireless network. This PC may be, for example, a colleague's computer or a meeting room computer or workstation. When the user returns to their office, any files recently downloaded to their mobile phone are automatically synchronized back to their office PC.

The benefit of using phone-resident data is that users need not rely on ubiquitous connectivity—collaboration is possible relying only on short range ad hoc transport protocols, such as Bluetooth. Also, because the technique, in one embodiment, employs short range point to point communication, it can often avoid the overhead of user authentication and data encryption.

It is noted that while the foregoing limitations in existing search schemes described in the Background section can be resolved by a particular implementation of the present collaborative phone-based file exchange technique, this is in no way limited to implementations that just solve any or all of the noted disadvantages. Rather, the present technique has a much wider application as will become evident from the descriptions to follow.

In the following description of embodiments of the present disclosure reference is made to the accompanying drawings which form a part hereof, and in which are shown, by way of illustration, specific embodiments in which the technique may be practiced. It is understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the present disclosure.

DESCRIPTION OF THE DRAWINGS

The specific features, aspects, and advantages of the disclosure will become better understood with regard to the following description, appended claims, and accompanying drawings where:

FIG. 1 is a diagram depicting a general purpose computing device constituting an exemplary system for a implementing a component of the present collaborative phone-based file exchange technique.

FIG. 2 provides an overview of an operating environment in which the present collaborative phone-based file exchange technique may typically be carried out.

FIG. 3 is a diagram depicting one exemplary architecture of the present collaborative phone-based file exchange technique.

FIG. 4 is a flow diagram depicting an exemplary embodiment of a process employing the present collaborative phone-based file exchange technique in synchronizing files between a mobile phone and a paired PC.

FIG. 5 is a flow diagram depicting an exemplary embodiment of a process employing the present collaborative phone-based file exchange technique in sharing files in a collaborative environment using one or more mobile phones and a PC.

FIG. 6 is an exemplary flow diagram depicting the processing performed by a mobile phone in order to synchronize files with a PC employed in one embodiment of the present collaborative phone-based file exchange technique.

FIG. 7 is an exemplary flow diagram depicting the processing performed by a PC in order to synchronize files with a mobile phone employed in one embodiment of the present collaborative phone-based file exchange technique.

FIG. 8 is an exemplary flow diagram depicting the processing performed by a mobile phone in order to share files in a collaborative environment using a PC employed in one embodiment of the present collaborative phone-based file exchange technique.

FIG. 9 is an exemplary flow diagram depicting the processing performed by a PC in order to share files in a collaborative environment using one or more mobile phones employed in one embodiment of the present collaborative phone-based file exchange technique.

FIG. 10 depicts a start up screen of an exemplary user interface of the present collaborative phone-based file exchange technique.

FIG. 11 depicts a status screen of an exemplary user interface of the present collaborative phone-based file exchange technique.

FIG. 12 depicts a shared items screen of an exemplary user interface of the present collaborative phone-based file exchange technique.

FIG. 13 depicts a screen for sharing items in an exemplary user interface of the present collaborative phone-based file exchange technique.

FIG. 14 depicts a file information screen of an exemplary user interface of the present collaborative phone-based file exchange technique.

FIG. 15 depicts a file detail screen of an exemplary user interface of the present collaborative phone-based file exchange technique.

DETAILED DESCRIPTION

1.0 The Computing Environment

Before providing a description of embodiments of the present collaborative phone-based file exchange technique, a brief, general description of a suitable computing environment in which portions thereof may be implemented will be described. The present technique is operational with numerous general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable include, but are not limited to, personal computers, server computers, hand-held or laptop devices (for example, media players, notebook computers, cellular phones, personal data assistants, voice recorders), multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.

FIG. 1 illustrates an example of a suitable computing system environment. The computing system environment is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the present collaborative phone-based file exchange technique. Neither should the computing environment be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment. With reference to FIG. 1, an exemplary system for implementing the present collaborative phone-based file exchange technique includes a computing device, such as computing device 100. In its most basic configuration, computing device 100 typically includes at least one processing unit 102 and memory 104. Depending on the exact configuration and type of computing device, memory 104 may be volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two. This most basic configuration is illustrated in FIG. 1 by dashed line 106. Additionally, device 100 may also have additional features/functionality. For example, device 100 may also include additional storage (removable and/or non-removable) including, but not limited to, magnetic or optical disks or tape. Such additional storage is illustrated in FIG. 1 by removable storage 108 and non-removable storage 110. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Memory 104, removable storage 108 and non-removable storage 110 are all examples of computer storage media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by device 100. Any such computer storage media may be part of device 100.

Device 100 has a display 118, and contains communications connection(s) 112 that allow the device to communicate with other devices. Communications connection(s) 112 is an example of communication media. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. The term computer readable media as used herein includes both storage media and communication media.

Device 100 may have various input device(s) 114 such as a keyboard, mouse, pen, camera, touch input device, and so on. Output device(s) 116 such as a speakers, a printer, additional displays, and so on may also be included. All of these devices are well known in the art and need not be discussed at length here.

The present collaborative phone-based file exchange technique may be described in the general context of computer-executable instructions, such as program modules, being executed by a computing device. Generally, program modules include routines, programs, objects, components, data structures, and so on, that perform particular tasks or implement particular abstract data types. The present collaborative phone-based file exchange technique may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The exemplary operating environment having now been discussed, the remaining parts of this description section will be devoted to a description of the program modules embodying the present collaborative phone-based file exchange technique.

2.0 Collaborative Phone-Based File Exchange Technique

The following sections provide an overview of the present collaborative phone-based file exchange technique, an exemplary operating environment, an exemplary architecture in which the technique can be practiced, exemplary processes employing the technique and exemplary user interfaces.

2.1 Overview

The present collaborative phone-based file exchange technique provides a conveniently-sized device that provides reliable access to a user's personal data and annexes nearby resources to support a rich collaboration experience.

The present collaborative phone-based file exchange technique automatically synchronizes a user's work context with his or her mobile phone, preferably using a wireless network, and makes this context readily available and sharable in collaborative situations. When the user is away from their desk, collaboration with others is possible by sharing/downloading between the mobile phone and a PC enabled with the present collaborative phone-based file exchange technique, which may be a colleague's computer or a meeting room workstation/computer. When the user returns to their office, any recently downloaded files are automatically synchronized back to their office PC. It should be noted that while a PC is referred to in this description of the present technique, this PC could actually be any type of computing device such as that described with respect to FIG. 1.

The present collaborative phone-based file exchange technique employs a set of programs running on a PC and a mobile phone, to facilitate access, display, manipulation and exchange of information resources between a knowledge worker's personal work context and collaborative gatherings.

In one embodiment, the present collaborative phone-based file exchange technique is designed to reliably access files and Uniform Resource Locators (URLs) from users' work context directly on their mobile phones. The present collaborative phone-based file exchange technique accomplishes this through automatic data caching from a user's PC to their mobile phone. An issue, however, is that mobile phone displays are not amenable to collaboration. Their small screen size makes it impractical for several users to collaborate on a set of documents. During face-to-face collaboration, therefore, the present collaborative phone-based file exchange technique assumes users want to see the files on which they are collaborating, and not just transfer them between devices.

The present collaborative phone-based file exchange technique allows a user to display and manipulate the files from users' mobile phones on a shared display. Instead of choosing between true multi-user input (which lacks widespread operating system support) and a more cumbersome approach of passing around a keyboard and mouse, the present collaborative phone-based file exchange technique offers a middle ground: users are given concurrent window-level control over shared documents from their phones. This allows users to perform browsing activities in parallel, but leaves floor control and detailed interaction of a file or document to a single user who is allowed to manipulate a displayed file with the input devices associated with the shared display.

Finally, collaboration involves the exchange of materials. Though email is by far the most common method of information exchange today, it places demands on both sender and receiver; senders must remember what to send and to whom to send it, as well as acquire the addresses of each recipient. Recipients must then file the sent data in a relevant local folder, or remember appropriate search criteria at a later date. The present collaborative phone-based file exchange technique eases the burdens of information exchange by allowing meeting participants to take the data of interest at the time of need, and by propagating and filing it automatically to their desktop PC when they reenter their workspace.

2.2 Exemplary Operating Environment

FIG. 2 provides a depiction of a typical environment in which the present collaborative phone-based file exchange technique can be practiced. In a most general sense, the technique can be used to automatically synchronize the files on a user's paired personal computer 202 and the user's mobile phone 204, typically using a wireless network 208. Alternately, the mobile phone 204 can be used in a shared environment via a meeting room PC or some other PC 206.

2.3 Exemplary Architecture of the Present Collaborative Phone-Based File Exchange Technique.

In the present collaborative phone-based file exchange technique, files and information are exchanged between a user's mobile phone and one or more personal computers. Hence, in one embodiment, a collaborative phone-based file exchange application employs two main configurations: a mobile configuration for the mobile phone and a desktop configuration for the PCs that communicate with the mobile phone.

FIG. 3 provides an exemplary architecture wherein the present collaborative phone-based file exchange technique can be practiced. Generally, in one embodiment, the collaborative phone-based file exchange architecture can include a standard individual user computing device or PC 302 (such as described with respect to FIG. 1). The individual PC 302 has a desktop configuration of the present collaborative phone-based file exchange application 304 installed on it for sending information to, and receiving information from, a mobile phone 306. It also has a display 330, a file database 324 and a wireless connection 326. The shared/meeting room PC 308 is similarly configured, with a desktop version of the present collaborative phone-based file exchange application 304 installed on it which can be used for displaying and manipulating files on a shared display 328. The individual user computing device or PC 302, and the shared/meeting room PC 308, could be in one of many configurations such as, for example, a desktop computer, a notebook computer, or a Tablet PC, to name a few. It should be also be noted that many mobile phones 306, individual's PCs 302 and shared/meeting room PCs 308 could be employed in the architecture of the present collaborative phone-based file exchange technique.

As mentioned above, the present collaborative phone-based file exchange architecture also has a mobile phone (for example, a Smartphone) 306 with wireless network connectivity 326 (for example, Bluetooth). The mobile phone is also a computing device (for example, such as described with respect to FIG. 1). It has a mobile version 314 of the present collaborative phone-based file exchange application installed on it for sending information to, and receiving information from, the individual user computing device 302 and the shared/meeting room computer 308. Additionally, it has a logging tool 322, a file database 334, a browser 336 and a display 338. These components will be discussed in greater detail in the paragraphs below.

The following paragraphs provide additional details of the desktop and mobile versions of the applications of the present collaborative phone-based file exchange technique.

2.3.1 Desktop Configuration.

One embodiment of the desktop configuration of the present collaborative phone-based file exchange technique offers two independent services: a “sync/upload” service 316, and a “share/download” service 318. In one embodiment it relies on a configuration file, read in on application startup, to determine whether to offer sync/upload 316, share/download 318, or both simultaneously. The sync/upload service 316 is designed to maintain a trusted, wireless “pairing” relationship for synchronizing files between a particular user's mobile phone 306 and their own personal computer 302, whereas the share/download service 318 is meant to support a “meeting” scenario which allows multiple concurrent users to join or create a meeting on a shared display 328 and to share or download files. For example, a share/download service 318 might be enabled on a user's PC is to allow visitors to the user's office to share files from their phones. A reason a share/download only configuration might be used is for meeting servers that are not associated with any one user as a PC. In one embodiment, each service is associated with a distinct Bluetooth service Globally Unique Identifier (GUID) so that clients can distinguish the services from one another. Upon startup, each service 316, 318 is preferably launched independently to await connection requests. When a service request from a mobile phone 306 is successfully accepted, a computing device with a desktop version of the application 302, 308 opens a dedicated connection to the device to handle commands, and returns to listening for new service requests from other devices.

2.3.2 Mobile Configuration.

The mobile phone in one embodiment of the present collaborative phone-based file exchange technique is configured with a mobile application of the present technique. The mobile configuration's user interface, which will be described in greater detail later, offers the user the ability to search for and connect to other devices configured with the collaborative phone-based file exchange application that are within range that are publishing the previously discussed desktop configuration share/download service 318. Once connected, the mobile phone configuration 306 works in conjunction with the desktop PC configurations 302, 308 to offer the user the ability to interactively exchange information and documents and control document windows on a shared display 318. Unlike the interactive share/download service 318, the mobile phone's sync/upload activity 316 operates without any user intervention. When the mobile application 314 is running, the sync/upload service 316 performs a periodic scan to determine whether the user's personal (paired) PC 302 is within wireless (e.g., Bluetooth) range. If so, the phone 306 connects to the paired PC and begins the synchronization process by requesting files that have changed since the last update.

In one embodiment, the present collaborative phone-based file exchange technique uses a logging tool 322 on both of the PCs 302, 308 and the mobile phone 306, to track the files and Uniform Resource Locator (URL) access activity that constitutes a user's work context. It is assumed that the files and URLs a user is mostly likely to share are those accessed in the relatively recent past, so the context window is set to a reasonable constant, such as, for example, two weeks. In another embodiment, the context window is controlled by the amount of free disk space available for storing the database and files. In either case the logging tool 322 creates a file database 324 of important documents, URLs and other pertinent files.

Consulting its local logging tool's database 324, the desktop application determines if any files have changed, and if so, sends each new or updated file to the paired mobile phone 306, thereby completing the synchronization process. For example, in one embodiment, for web links, the streamed file is simply a “.url” file containing the URL to the web page, whereas for non-web file types (such as “.doc” or “.pdf” files) the file contents are transmitted in binary format and a full copy is thus created on the receiving device. The mobile phone configuration 306 of the present collaborative phone-based file exchange technique then checks if it has any files downloaded from a shared/meeting room PC 308 or other device enabled with the present collaborative phone-based file exchange technique that have not yet been sent back to the paired PC 302. If so, these files are streamed back to the desktop PC 302, 308 and stored in a folder whose name encodes the time and PC name of the meeting from which the files were obtained, thereby completing the upload process. This two-way sync/upload synchronization is repeated periodically as long as the paired connection is maintained. When the connection is lost, in one embodiment of the present collaborative phone-based file exchange technique, the mobile configuration tries to re-establish it repeatedly on a decaying time schedule with increasingly long pauses between retries.

In one embodiment, the present collaborative phone-based file exchange technique connections adhere to a request/response model with the mobile configuration as the client and the desktop configuration as the server. Each mobile instance is serviced by an independent desktop thread, which allows a device to easily repair a dropped connection, and isolates each device from faults caused by other devices.

2.4 Exemplary Processes Employing the Present Collaborative Phone-Based File Exchange.

As discussed above, the present collaborative phone-based file exchange technique can be described in terms of the sync/upload interaction from the viewpoint of the PC and also from the viewpoint of the mobile phone. This interaction takes place when syncing the data between the mobile phone and a user's paired computer. Additionally, the technique can be described in terms of the share/download interaction between the PC in a meeting mode and the mobile phone from the viewpoint of the PC and also from the viewpoint of the mobile phone. This interaction takes place when the mobile phone and a PC are in a meeting/sharing mode. Examples of these processes are discussed in the paragraphs below.

An overview of one exemplary embodiment of the syncing process is shown in FIG. 4. As shown in box 402, a PC creates a database of important files and associated file usage data by logging activity on the PC. The PC then connects/pairs with a mobile phone (box 404) and important files and file usage data on the PC and the mobile phone are compared (box 406). Files that are new or have changed since the last connection between the PC and mobile phone, are transferred to the mobile phone (box 408). Likewise, new files on the mobile phone that have not previously been sent to the paired PC are transferred to the PC (box 410) and may be integrated into its database of important files.

An overview of one exemplary embodiment of the sharing process is shown in FIG. 5. In this embodiment a mobile phone finds a PC that is sending a meeting broadcast (box 502) and acknowledges this PC (box 504). The PC then adds the mobile phone to the meeting (box 506), and sends the mobile phone an attendee list and a shared file list (box 508). The PC then manages the meeting and allows the mobile phone user to display and manipulate files on a shared display (box 510). If a mobile phone requests an updated attendee list or a shared file list, this is sent (boxes 512, 508) If another mobile phone acknowledges the PC's meeting broadcast, the PC repeats the process (boxes 506, 508, 510, 512, 514). Once the last meeting attendee (mobile phone) leaves the meeting (box 516), the meeting ends.

The process shown in FIG. 6 provides an example of the sync/upload processing that occurs at the mobile phone. Initially, the mobile phone looks for a paired desktop computer that is within range (box 602). Typically, in one embodiment, the pairing takes place over a limited range wireless network, such a Bluetooth network. Once the mobile phone finds the paired desktop configuration it connects to it (box 604). It then accesses a list of files on the mobile phone which are time-stamped with the date they were created or last changed (box 606). The mobile phone also receives from the paired PC a list of files that reside on the paired PC (box 608). The list of files on the paired PC are also annotated with information as to when they were created or last changed. The mobile phone then calculates the files it needs by comparing the list of files on the phone to the list of files on the paired PC (box 610). It then produces a list of files it needs (box 612) and sends this list of files to the paired PC (box 614). The mobile phone then receives the files that are new or have changed from the desktop PC (box 616). The mobile phone then checks if it has any files that it downloaded from a meeting room PC or other site that it has not yet sent to the paired PC (box 618). If so, it sends these files to the paired PC (box 620). If the mobile phone does not have any files to send, it continues checking if it is still paired to the desktop PC, and if it is it continues the process until it is not paired anymore (boxes 606 through 622), in which case it attempts to reestablish the paired connection periodically (box 622, 602).

An exemplary process from the point of view of the PC of syncing and uploading files to the paired mobile phone is shown in FIG. 7. At the PC a logging tool continually watches for activity and writes files changed by this activity to a file database (box 702). The logging tool records activity on the PC, for example, activity in applications, the operating system, the activity of input devices and other similar activities, all which are time-stamped. The paired PC reads the database and builds a list of important files that it holds (boxes 704). When the PC pairs to a mobile phone in range and a list of important files is requested by the mobile phone, the paired PC sends the list of the important files to the paired mobile phone (box 706, 708, 710), which, as discussed above, compares this list to the files it holds, and requests files that it needs from the paired PC. (It should be noted that this comparison could equally well be performed by the PC.) The paired PC receives this request (box 712) and sends the requested files to the mobile phone (box 714). Additionally, it receives from the mobile phone new files the phone holds (box 716).

An exemplary process wherein a mobile phone shares documents, or joins a meeting, is shown in FIG. 8. This process takes place in a share/download mode. As shown in FIG. 8, the mobile phone looks for a desktop PC that is transmitting a meeting broadcast (e.g. the previously discussed share/download service) on a limited range wireless network (e.g., Bluetooth) (box 802). For example, in one embodiment, the PC adheres to one (and possibly more) standardized service publishing formats. For example, Bluetooth has a standardized way of broadcasting services, which are identified by means of a unique universal identifier. With Bluetooth, the mobile phone first looks for *all* discoverable Bluetooth devices within range, and then checks each to see if they offer the share/download service (a unique universal id). Other service publishing protocols exist and could be used as appropriate, for example 802.11 communication. Once the mobile phone finds the meeting broadcast it acknowledges its presence to the broadcasting PC (box 804). It also receives a list of the shared files and meeting attendee list from the desktop PC (which is typically operating in a server mode) (box 806). If the user wants to share any files, the mobile phone uploads these from the PC (boxes 808, 810). The mobile phone then participates in the meeting by viewing and manipulating files on a shared display (box 812).

An exemplary process wherein a PC is in meeting mode is shown in FIG. 9. The PC (operating in a server mode) transmits a meeting broadcast (box 902). It then receives a connection from a mobile phone and acknowledges it (boxes 904, 906). The desktop PC then adds the person corresponding to the mobile phone to the meeting attendee list (box 908) and transmits the attendee list and the list of shared files to the connected mobile phone (box 910). The desktop PC then waits for and executes commands from the connected mobile phone(s) (box 912). These commands can include, for example, requesting a list of meeting attendees, requesting a list of shared files, sharing a file, unsharing a file, downloading a file, requesting attendee details, and commands to control the window of a shared file, to name a few.

2.5 User Interface Design

The following section describes exemplary user interface components of one embodiment of the present collaborative phone-based file exchange technique and the workings of the share/download service in greater detail. In one embodiment, on the mobile phone, the present collaborative phone-based file exchange technique offers an initial status screen 1002 (as shown in FIG. 10) of service activity, and a menu of commands at the bottom right 1004. Selecting the “Join Meeting” command 1006 from the menu initiates a search via a limited range wireless network, such as, for example, Bluetooth, and returns a list of available meeting PCs (devices within wireless network range that are publishing the share/download service), allowing the user to select one to connect to. When the first mobile phone connects to a given PC's share/download service, the desktop PC begins a “meeting” by noting the time of connection. It subsequently tracks the number of users connected and the files each have shared, and sends updates of this information to each connected device (“meeting attendee”) whenever there are changes. Once having joined to (or started) a meeting, the main mobile meeting screen 1102 (shown in FIG. 11) shows this continually-updated view of meeting status.

The Shared Items screen (shown in FIG. 12, 1202) shows a list of all files that are currently available (shared) in the context of the meeting. In this exemplary embodiment, bolded items are those being shared by the phone's user, and non-bolded items are those shared by others. Sharing ownership is important because, in one embodiment, the present collaborative phone-based file exchange technique enforces a semantic that, while shared files can be viewed, manipulated, or downloaded by any attendee, they can only be unshared (revoked from the public meeting) by the attendee that originally shared them. The icons to the right of each line 1208, together with the left context menu, indicate the available operation for each file: “Stop Sharing” 1204 (for files the user has shared) or “Download” (not shown) (for files others have shared). When the user chooses to “Download,” the file is streamed from the meeting PC to the local phone. When the user chooses to “Stop Sharing,” 1204 1) the shared file is removed from the public meeting lists, 2) the associated window on the meeting PC is closed, and 3) the file is deleted from the meeting PC. (Any copies already downloaded by other attendees are unaffected, however.) In order to share a new item from the mobile phone to the public meeting space, the user selects “Share an Item . . . ” 1206, (or 1104 of FIG. 11) from any available menu (e.g. the meeting overview screen in FIG. 11 or the Shared Items screen in FIG. 12). In one embodiment, this takes the user to a specialized file browser 1304 of phone-resident files, as shown in FIG. 13. The file browser 1304 displays local files in a flat list by name rather than in a folder hierarchy by location. To help users find desired items, the files are grouped into separate tabs 1306 by file type; the left/right directional navigation hardware navigates among tabs. Within a tab 1306, users can sort the items by name, length of access, and last access time from the right menu. This information is tracked by the logging tool, which provides document usage information not offered by the file system. In this way, the browser provides a personalized view of a user's files based on their desktop work history. In one embodiment the default ordering of files is by last access time, under the assumption that the files users are most likely to share are the ones they have recently accessed.

In one embodiment, items that are currently being shared are shown in bold. After highlighting a file in the list, the user can choose to share it (if unshared, otherwise the user can choose to unshare it) immediately by pressing the left menu button, or get more information about the file by pressing a select key. In one embodiment, the file details screen 1402 (shown in FIG. 14) shows the title of the file, the URL (for a web file) or original file path (for non-web files), as well as a small thumbnail of the file. The status area 1404 at the top of the details page indicates “Unshared” if the file is not currently shared (or “Shared” if the file is in fact presently shared). When the “Share” menu button 1406 is pressed, the mobile phone streams the file to the meeting PC, where the file is opened, displayed, and made available to other meeting attendees. The file's local status changes to “Shared” and the interface transitions to the Shared File Details screen 1502 (shown in FIG. 15), where the user can proceed to manipulate the file on the shared display. In addition, the Shared File Details screen 1502 is reachable (via the Shared Items list in FIG. 12, 1202) for any shared file in the meeting space. Since each shared file corresponds to an open window on the meeting PC's shared display, this screen offers the user the ability to send various control commands to the open window using the keypad (for instance, scrolling the window contents with ‘3’ or ‘9’ or moving it around the display with the joystick). The PC maintains a mapping between each file and its associated window, and posts messages to that window when control commands (such as move or scroll) come in from any of the connected mobile phones for the corresponding shared file.

The present collaborative phone-based file exchange technique allows people to use their mobile phone to browse their recently-visited URLs and send them to people. Meeting participants can use their phone to send documents and URLs of interest to a large meeting room display. The visuals improve meeting productivity by conveying ideas faster than words. Furthermore, time and effort can be saved since meeting members can use their phones to acquire any or all of the materials presented at the meeting, both as an archive of the topics discussed, and to jump start follow-up research when they return to their offices.

It should also be noted that any or all of the aforementioned alternate embodiments may be used in any combination desired to form additional hybrid embodiments. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. For example, although this description refers to a mobile phone, other portable computing devices that have wireless access and are configured with the components of present collaborative file-exchange technique cold be used instead of the mobile phone. This is especially true if such portable computing devices become as ubiquitous as mobile phones are today. The specific features and acts described above are disclosed as example forms of implementing the claims. 

Wherefore, what is claimed is:
 1. A computer-implemented process for handing off application data between a first computing device and a second computing device, comprising: while a user is performing a task with a first application on the first computing device, determining whether a service that maintains a trusted pairing relationship between the first computing device and the second computing device is enabled on the first computing device and on the second computing device; whenever the service is enabled on both the first computing device and the second computing device, pairing the first computing device, having the first application, with the second computing device, the second computing device having a second application compatible with the first application; transferring application data associated with the first application from the first computing device to the second application on the second computing device; while the user is performing a task with the second application on the second computing device when the service is enabled on both the first computing device and the second computing device, transferring application data associated with the second application from the second computing device to the first application on the first computing device.
 2. The computer-implemented process of claim 1, wherein the service is identified with a unique identifier to allow the first computing device and the second computing device to identify and access the service.
 3. The computer-implemented process of claim 1, wherein the first computing device and the second computing device must be within a prescribed range of each other for the application data transfer to occur.
 4. The computer-implemented process of claim 1, wherein multiple instances of application data can be transferred and displayed on a display of the second computing device simultaneously.
 5. The computer-implemented process of claim 1, wherein the application data is an email message and wherein the compatible applications are email applications.
 6. The computer-implemented process of claim 1, wherein the application data is an electronic document and wherein the compatible applications are productivity applications.
 7. The computer-implemented process of claim 1, wherein the application data is a Uniform Resource Locator (URL) and wherein the compatible applications are browser applications.
 8. The computer-implemented process of claim 1, wherein the application data is a contact and wherein the compatible applications are contact management applications.
 9. The computer-implemented process of claim 1, wherein at least one of the first computing device or the second computing device is a mobile computing device.
 10. The computer-implemented process of claim 1, wherein determining whether the service that maintains a trusted pairing relationship between the first computing device and the second computing device is enabled on the first computing device and on the second computing device, further comprises using a configuration file.
 11. A computer-implemented process for handing off application data between a mobile computing device and a first computing device using a second computing device, comprising: determining whether a share/download service is enabled on the mobile computing device, wherein the share/download service allows multiple concurrent users to share application data on the second computing device; if the share/download service is enabled on the mobile computing device, sending to a first application associated with the mobile computing device, from the second computing device, application data associated with a second application on the second computing device, said second application being compatible with the first application; determining whether a sync/upload service that enables a trusted pairing relationship between the mobile computing device and the first computing device is enabled on the mobile computing device and on the first computing device; whenever the sync/upload service is enabled on both the mobile computing device and the first computing device, pairing the mobile computing device with the first computing device and transferring the application data from the mobile computing device to a third application on the first computing device, wherein the third application is compatible with the first application.
 12. The computer-implemented process of claim 11, wherein the first computing device connects to the mobile computing device via a limited range wireless network.
 13. The computer-implemented process of claim 12, wherein the limited range wireless network is a Bluetooth network.
 14. The computer-implemented process of claim 11, further comprising: launching the third application on the first computing device after transfer of the application data from the mobile computing device to the first computing device; and displaying the transferred application data on the first computing device.
 15. A computer-implemented process for handing off a task between a first computing device and a second computing device, comprising: a user beginning to perform a task with a first application on the first computing device; determining whether a service that maintains a trusted pairing relationship between the first computing device and the second computing device is enabled on the first computing device and on the second computing device; whenever the service is enabled on both the first computing device and the second computing device, transferring the task from the first application on the first computing device to a second application on the second computing device, wherein the second application is compatible with the first application; and the user continuing to perform the task with the second application on the second computing device.
 16. The computer-implemented process of claim 15 wherein multiple tasks are transferred to the second application on the second computing device.
 17. The computer-implemented process of claim 16 further comprising the user continuing to perform the multiple transferred tasks on the second computing device.
 18. The computer-implemented process of claim 15 wherein the first computing device pairs to the second computing device via a limited range wireless network.
 19. The computer-implemented process of claim 15 wherein determining whether the service that maintains a trusted pairing relationship is enabled on the first computing device and on the second computing device, further comprises the service using a configuration file on the first computing device and the second computing device.
 20. A computer-implemented process for synchronizing files between a mobile computing device and a first computing device, comprising: determining whether a file sharing download service is enabled on the mobile computing device, wherein the file sharing download service allows multiple concurrent users to share files on a second computing device on which sharing is enabled; if the file sharing download service is enabled on the mobile computing device, receiving file modifications, deletions and additions for files on the mobile computing device from the second computing device; determining whether a sync service that maintains a trusted synced relationship between the mobile computing device and the first computing device is enabled on the mobile computing device and on the first computing device; if the sync service is enabled on both the mobile computing device and the first computing device, automatically synchronizing the files on the mobile computing device with the files on the first computing device.
 21. The computer-implemented process of claim 20 wherein the download shared files service on the second computing device supports concurrent access by the multiple users to the shared files on the second computer. 